Default pdsch beam setting and pdcch prioritization for multi panel reception

ABSTRACT

Various embodiments herein are directed to set physical downlink shared channel (PDSCH) default beam behavior for single transmission-reception point (TRP), single downlink control information (DCI) multi-TRP and multi-DCI multi-TRP operation, as well as physical downlink control channel (PDCCH) prioritization based on quasi-colocation (QCL) Type-D for multi-panel reception and single panel reception.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional PatentApplication No. 62/976,953, which was filed Feb. 14, 2020; thedisclosure of which is hereby incorporated by reference.

FIELD

Embodiments relate generally to the technical field of wirelesscommunications.

BACKGROUND

PDSCH default beam behavior is unknown when UE is configured withdifferent CORESETPoolIndex values with all TCI codepoints are mapped toone TCI state. Due to PDCCH prioritization, PDCCHs corresponding to oneof the panels will not be monitored disallowing multi-DCI multi-TRPoperation. Embodiments of the present disclosure address these and otherissues.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example and not by wayof limitation in the figures of the accompanying drawings.

FIGS. 1A, 1B, and 1C illustrate examples of operation flow/algorithmicstructures in accordance with some embodiments.

FIG. 2 illustrates an example of a network in accordance with variousembodiments.

FIG. 3 schematically illustrates a wireless network in accordance withvarious embodiments.

FIG. 4 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers may be used in different drawings to identifythe same or similar elements. In the following description, for purposesof explanation and not limitation, specific details are set forth suchas particular structures, architectures, interfaces, techniques, etc. inorder to provide a thorough understanding of the various aspects ofvarious embodiments. However, it will be apparent to those skilled inthe art having the benefit of the present disclosure that the variousaspects of the various embodiments may be practiced in other examplesthat depart from these specific details. In certain instances,descriptions of well-known devices, circuits, and methods are omitted soas not to obscure the description of the various embodiments withunnecessary detail. For the purposes of the present document, thephrases “A or B” and “A/B” mean (A), (B), or (A and B).

In this disclosure, the following aspects related to multi-TRP operationare addressed:

-   -   How to set PDSCH default beam behavior for single TRP, single        DCI multi-TRP and multi-DCI multi-TRP operation; and    -   PDCCH prioritization based on QCL Type-D for multi-panel        reception and single panel reception.

Ideas presented in this disclosure allow a UE to monitor PDCCH frommultiple TRPs for both single DCI multi-TRP and multi-DCI multi-TRPoperation.

PDCCH+PDCCH Prioritization Prioritization Limited to Single TRP andSingle DCI Multi-TRP Operation:

Currently PDCCH prioritization in 38.213 is naturally applicable to bothsingle TRP operation and multi-DCI multi-TRP reception. But as a resultof this prioritization, PDCCHs corresponding to one of the Rx panelswill not be monitored. The proposal is to remove the applicability ofthe PDCCH prioritization from multi-DCI multi-TRP operation. As a resultthe PDCCH prioritization is applicable to single TRP operation (all DCIcodepoints are single-TCI with CORESETPoolIndex with different valuesnot configured) and single DCI multi-TRP operation (at least one DCIcodepoint has 2 TCI states). This also implies that in single DCImulti-TRP operation, in case of time-overlap of search spaces, PDCCHmonitoring occurs from a single TRP.

Text proposal for section 10.1 in 38.213:

If a UE

-   -   is configured for single cell operation or for operation with        carrier aggregation in a same frequency band, and    -   monitors PDCCH candidates in overlapping PDCCH monitoring        occasions in multiple CORESETs that have same or different        QCL-TypeD properties on active DL BWP(s) of one or more cells,        and    -   is not configured with two different values of CORESETPoolIndex        in ControlResourceSet        -   the UE monitors PDCCHs only in a CORESET, and in any other            CORESET from the multiple CORESETs having same QCL-TypeD            properties as the CORESET, on the active DL BWP of a cell            from the one or more cells    -   the CORESET corresponds to the CSS set with the lowest index in        the cell with the lowest index containing CSS, if any;        otherwise, to the USS set with the lowest index in the cell with        lowest index    -   the lowest USS set index is determined over all USS sets with at        least one PDCCH candidate in overlapping PDCCH monitoring        occasions    -   for the purpose of determining the CORESET, a SS/PBCH block is        considered to have different QCL-Type D properties than a CSI-RS    -   for the purpose of determining the CORESET, a first CSI-RS        associated with a SS/PBCH block in a first cell and a second        CSI-RS in a second cell that is also associated with the SS/PBCH        block are assumed to have same QCL-TypeD properties    -   the allocation of non-overlapping CCEs and of PDCCH candidates        for PDCCH monitoring is according to all search space sets        associated with the multiple CORESETs on the active DL BWP(s) of        the one or more cells    -   the number of active TCI states is determined from the multiple        CORESETs

Prioritization Extended to Multi-DCI Multi-TRP Operation:

The PDCCH prioritization technique can be extended to multi-DCImulti-panel operation (CORESETPoolIndex with different valuesconfigured) by specifying the prioritization operation within the set ofCORESETs within and across cells associated with the same value ofCORESETPoolIndex. This can be specified by the following:

Text proposal for section 10.1 in 38.213:

If a UE

-   -   is configured for single cell operation or for operation with        carrier aggregation in a same frequency band, and    -   is configured with two different values of CORESETPoolIndex in        ControlResourceSet, and    -   monitors PDCCH candidates in overlapping PDCCH monitoring        occasions in multiple CORESETs that are associated with the same        value of CORESETPoolIndex and have same or different QCL-Type D        properties on active DL BWP(s) of one or more cells    -   the UE monitors PDCCHs only in a CORESET, and in any other        CORESET from the multiple CORESETs having the same QCL-TypeD        properties as the CORESET, on the active DL BWP of a cell from        the one or more cells    -   the CORESET corresponds to the CSS set with the lowest index in        the cell with the lowest index containing CSS, if any;        otherwise, to the USS set with the lowest index in the cell with        lowest index    -   the lowest USS set index is determined over all USS sets with at        least one PDCCH candidate in overlapping PDCCH monitoring        occasions    -   for the purpose of determining the CORESET, a SS/PBCH block is        considered to have different QCL-TypeD properties than a CSI-RS    -   for the purpose of determining the CORESET, a first CSI-RS        associated with a SS/PBCH block in a first cell and a second        CSI-RS in a second cell that is also associated with the SS/PBCH        block are assumed to have same QCL-TypeD properties    -   the allocation of non-overlapping CCEs and of PDCCH candidates        for PDCCH monitoring is according to all search space sets        associated with the multiple CORESETs on the active DL BWP(s) of        the one or more cells    -   the number of active TCI states is determined from the multiple        CORESETs

Prioritization Enhanced for Single DCI Multi-TRP Operation:

The PDCCH prioritization technique can be enhanced for single DCImulti-TRP operation (at least one DCI codepoint has 2 TCI states) toallow PDCCH monitoring from 2 TRPs in case of time-overlap of searchspaces. In this case multiple CORESETs within and across cells areassociated with the same TCI group. A TCI-group can be characterized as:

-   -   a TCI-group comprises of TCI-states associated with the same        reception panel    -   two TCI-States in different cells are associated with the same        reception panel if they have the same TCI-State-Id    -   TCI-States associated with CORESETs that are in turn associated        with the same CORESETPoolIndex value (if configured) are        associated with the same reception panel    -   TCI-States associated with the same value of panel index are        associated with the same reception panel    -   Two TCI-States comprising of CRI or SSBRI that are reported in a        single reporting instance are not associated with the same        reception panel    -   Reporting of CRI/SSBRI is ordered such that in a single        CSI-report with groupBasedBeamReporting enabled, the first        CRI/SSBRI is associated with the first reception panel and the        second CRI/SSBRI is associated with the second reception panel.

If a UE:

-   -   is configured for single cell operation or for operation with        carrier aggregation in a same frequency band, and    -   monitors PDCCH candidates in overlapping PDCCH monitoring        occasions in multiple CORESETs that are associated with the same        TCI-group and have same or different QCL-Type D properties on        active DL BWP(s) of one or more cells    -   the UE monitors PDCCHs only in a CORESET, and in any other        CORESET from the multiple CORESETs having the same QCL-TypeD        properties as the CORESET, on the active DL BWP of a cell from        the one or more cells    -   the CORESET corresponds to the CSS set with the lowest index in        the cell with the lowest index containing CSS, if any;        otherwise, to the USS set with the lowest index in the cell with        lowest index    -   the lowest USS set index is determined over all USS sets with at        least one PDCCH candidate in overlapping PDCCH monitoring        occasions    -   for the purpose of determining the CORESET, a SS/PBCH block is        considered to have different QCL-TypeD properties than a CSI-RS    -   for the purpose of determining the CORESET, a first CSI-RS        associated with a SS/PBCH block in a first cell and a second        CSI-RS in a second cell that is also associated with the SS/PBCH        block are assumed to have same QCL-TypeD properties    -   the allocation of non-overlapping CCEs and of PDCCH candidates        for PDCCH monitoring is according to all search space sets        associated with the multiple CORESETs on the active DL BWP(s) of        the one or more cells    -   the number of active TCI states is determined from the multiple        CORESETs

Distinction of Default PDSCH Default Beams:

Three different PDSCH default beam settings can be defined:

-   -   a) Single PDSCH default beam setting (Rel-15) enabled when all        TCI codepoints are mapped to one TCI state and UE is not        configured with different CORESETPoolIndex values    -   b) 2 default PDSCH default beam setting based on        CORESETPoolIndex which is enabled when a UE is configured with        different CORESETPoolIndex values. In this case, gNB through        implementation may set all TCI codepoints mapped to one TCI        state.    -   c) 2 default PDSCH default beam setting based on lowest TCI        codepoint enabled by a TCI codepoint indicating two TCI states.

The current text in 38.213 omits the underlined condition above. As aresult both behaviour a) and b) becomes applicable when a UE isconfigured with different CORESETPoolIndex values with all TCIcodepoints are mapped to one TCI state. The following text proposal addsthis condition to behaviour a).

Independent of the configuration of tci-PresentInDCI andtci-PresentInDCI-ForFormat1_2 in RRC connected mode, if all the TCIcodepoints are mapped to a single TCI state and the UE is not configuredwith two different values of CORESETPoolIndex in ControlResourceSet andthe offset between the reception of the DL DCI and the correspondingPDSCH is less than the threshold timeDurationForQCL, the UE may assumethat the DM-RS ports of PDSCH of a serving cell are quasi co-locatedwith the RS(s) with respect to the QCL parameter(s) used for PDCCH quasico-location indication of the CORESET associated with a monitored searchspace with the lowest controlResourceSetId in the latest slot in whichone or more CORESETs within the active BWP of the serving cell aremonitored by the UE. In this case, if the ‘QCL-TypeD’ of the PDSCH DM-RSis different from that of the PDCCH DM-RS with which they overlap in atleast one symbol, the UE is expected to prioritize the reception ofPDCCH associated with that CORESET. This also applies to the intra-bandCA case (when PDSCH and the CORESET are in different componentcarriers). If none of configured TCI states for the serving cell ofscheduled PDSCH contains ‘QCL-TypeD’, the UE shall obtain the other QCLassumptions from the indicated TCI states for its scheduled PDSCHirrespective of the time offset between the reception of the DL DCI andthe corresponding PDSCH. If a UE configured by higher layer parameterPDCCH-Config that contains two different values of CORESETPoolIndex inControlResourceSet, for both cases, when tci-PresentInDCI is set to‘enabled’ and tci-PresentInDCI is not configured in RRC connected mode,if the offset between the reception of the DL DCI and the correspondingPDSCH is less than the threshold timeDurationForQCL, the UE may assumethat the DM-RS ports of PDSCH associated with a value ofCORESETPoolIndex of a serving cell are quasi co-located with the RS(s)with respect to the QCL parameter(s) used for PDCCH quasi co-locationindication of the CORESET associated with a monitored search space withthe lowest CORESET-ID among CORESETs, which are configured with the samevalue of CORESETPoolIndex as the PDCCH scheduling that PDSCH, in thelatest slot in which one or more CORESETs associated with the same valueof CORESETPoolIndex as the PDCCH scheduling that PDSCH within the activeBWP of the serving cell are monitored by the UE. If the offset betweenthe reception of the DL DCI and the corresponding PDSCH is less than thethreshold timeDurationForQCL and at least one configured TCI states forthe serving cell of scheduled PDSCH contains the ‘QCL-TypeD’, and atleast one TCI codepoint indicates two TCI states, the UE may assume thatthe DM-RS ports of PDSCH of a serving cell are quasi co-located with theRS(s) with respect to the QCL parameter(s) associated with the TCIstates corresponding to the lowest codepoint among the TCI codepointscontaining two different TCI states.

Systems and Implementations

FIGS. 2-3 illustrate various systems, devices, and components that mayimplement aspects of disclosed embodiments.

FIG. 2 illustrates a network 200 in accordance with various embodiments.The network 200 may operate in a manner consistent with 3GPP technicalspecifications for LTE or 5G/NR systems. However, the exampleembodiments are not limited in this regard and the described embodimentsmay apply to other networks that benefit from the principles describedherein, such as future 3GPP systems, or the like.

The network 200 may include a UE 202, which may include any mobile ornon-mobile computing device designed to communicate with a RAN 204 viaan over-the-air connection. The UE 202 may be, but is not limited to, asmartphone, tablet computer, wearable computer device, desktop computer,laptop computer, in-vehicle infotainment, in-car entertainment device,instrument cluster, head-up display device, onboard diagnostic device,dashtop mobile equipment, mobile data terminal, electronic enginemanagement system, electronic/engine control unit, electronic/enginecontrol module, embedded system, sensor, microcontroller, controlmodule, engine management system, networked appliance, machine-typecommunication device, M2M or D2D device, IoT device, etc.

In some embodiments, the network 200 may include a plurality of UEscoupled directly with one another via a sidelink interface. The UEs maybe M2M/D2D devices that communicate using physical sidelink channelssuch as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 202 may additionally communicate with an AP206 via an over-the-air connection. The AP 206 may manage a WLANconnection, which may serve to offload some/all network traffic from theRAN 204. The connection between the UE 202 and the AP 206 may beconsistent with any IEEE 802.11 protocol, wherein the AP 206 could be awireless fidelity (Wi-Fi®) router. In some embodiments, the UE 202, RAN204, and AP 206 may utilize cellular-WLAN aggregation (for example,LWA/LWIP). Cellular-WLAN aggregation may involve the UE 202 beingconfigured by the RAN 204 to utilize both cellular radio resources andWLAN resources.

The RAN 204 may include one or more access nodes, for example, AN 208.AN 208 may terminate air-interface protocols for the UE 202 by providingaccess stratum protocols including RRC, PDCP, RLC, MAC, and L1protocols. In this manner, the AN 208 may enable data/voice connectivitybetween CN 220 and the UE 202. In some embodiments, the AN 208 may beimplemented in a discrete device or as one or more software entitiesrunning on server computers as part of, for example, a virtual network,which may be referred to as a CRAN or virtual baseband unit pool. The AN208 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU,TRxP, TRP, etc. The AN 208 may be a macrocell base station or a lowpower base station for providing femtocells, picocells or other likecells having smaller coverage areas, smaller user capacity, or higherbandwidth compared to macrocells.

In embodiments in which the RAN 204 includes a plurality of ANs, theymay be coupled with one another via an X2 interface (if the RAN 204 isan LTE RAN) or an Xn interface (if the RAN 204 is a 5G RAN). The X2/Xninterfaces, which may be separated into control/user plane interfaces insome embodiments, may allow the ANs to communicate information relatedto handovers, data/context transfers, mobility, load management,interference coordination, etc.

The ANs of the RAN 204 may each manage one or more cells, cell groups,component carriers, etc. to provide the UE 202 with an air interface fornetwork access. The UE 202 may be simultaneously connected with aplurality of cells provided by the same or different ANs of the RAN 204.For example, the UE 202 and RAN 204 may use carrier aggregation to allowthe UE 202 to connect with a plurality of component carriers, eachcorresponding to a Pcell or Scell. In dual connectivity scenarios, afirst AN may be a master node that provides an MCG and a second AN maybe secondary node that provides an SCG. The first/second ANs may be anycombination of eNB, gNB, ng-eNB, etc.

The RAN 204 may provide the air interface over a licensed spectrum or anunlicensed spectrum. To operate in the unlicensed spectrum, the nodesmay use LAA, eLAA, and/or feLAA mechanisms based on CA technology withPCells/Scells. Prior to accessing the unlicensed spectrum, the nodes mayperform medium/carrier-sensing operations based on, for example, alisten-before-talk (LBT) protocol.

In V2X scenarios the UE 202 or AN 208 may be or act as a RSU, which mayrefer to any transportation infrastructure entity used for V2Xcommunications. An RSU may be implemented in or by a suitable AN or astationary (or relatively stationary) UE. An RSU implemented in or by: aUE may be referred to as a “UE-type RSU”; an eNB may be referred to asan “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and thelike. In one example, an RSU is a computing device coupled with radiofrequency circuitry located on a roadside that provides connectivitysupport to passing vehicle UEs. The RSU may also include internal datastorage circuitry to store intersection map geometry, trafficstatistics, media, as well as applications/software to sense and controlongoing vehicular and pedestrian traffic. The RSU may provide very lowlatency communications required for high speed events, such as crashavoidance, traffic warnings, and the like. Additionally oralternatively, the RSU may provide other cellular/WLAN communicationsservices. The components of the RSU may be packaged in a weatherproofenclosure suitable for outdoor installation, and may include a networkinterface controller to provide a wired connection (e.g., Ethernet) to atraffic signal controller or a backhaul network.

In some embodiments, the RAN 204 may be an LTE RAN 210 with eNBs, forexample, eNB 212. The LTE RAN 210 may provide an LTE air interface withthe following characteristics: SCS of 15 kHz; CP-OFDM waveform for DLand SC-FDMA waveform for UL; turbo codes for data and TBCC for control;etc. The LTE air interface may rely on CSI-RS for CSI acquisition andbeam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRSfor cell search and initial acquisition, channel quality measurements,and channel estimation for coherent demodulation/detection at the UE.The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 204 may be an NG-RAN 214 with gNBs, forexample, gNB 216, or ng-eNBs, for example, ng-eNB 218. The gNB 216 mayconnect with 5G-enabled UEs using a 5G NR interface. The gNB 216 mayconnect with a 5G core through an NG interface, which may include an N2interface or an N3 interface. The ng-eNB 218 may also connect with the5G core through an NG interface, but may connect with a UE via an LTEair interface. The gNB 216 and the ng-eNB 218 may connect with eachother over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NGuser plane (NG-U) interface, which carries traffic data between thenodes of the NG-RAN 214 and a UPF 248 (e.g., N3 interface), and an NGcontrol plane (NG-C) interface, which is a signaling interface betweenthe nodes of the NG-RAN 214 and an AMF 244 (e.g., N2 interface).

The NG-RAN 214 may provide a 5G-NR air interface with the followingcharacteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDMfor UL; polar, repetition, simplex, and Reed-Muller codes for controland LDPC for data. The 5G-NR air interface may rely on CSI-RS,PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR airinterface may not use a CRS, but may use PBCH DMRS for PBCHdemodulation; PTRS for phase tracking for PDSCH; and tracking referencesignal for time tracking. The 5G-NR air interface may operating on FR1bands that include sub-6 GHz bands or FR2 bands that include bands from24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB thatis an area of a downlink resource grid that includes PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWPs forvarious purposes. For example, BWP can be used for dynamic adaptation ofthe SCS. For example, the UE 202 can be configured with multiple BWPswhere each BWP configuration has a different SCS. When a BWP change isindicated to the UE 202, the SCS of the transmission is changed as well.Another use case example of BWP is related to power saving. Inparticular, multiple BWPs can be configured for the UE 202 withdifferent amount of frequency resources (for example, PRBs) to supportdata transmission under different traffic loading scenarios. A BWPcontaining a smaller number of PRBs can be used for data transmissionwith small traffic load while allowing power saving at the UE 202 and insome cases at the gNB 216. A BWP containing a larger number of PRBs canbe used for scenarios with higher traffic load.

The RAN 204 is communicatively coupled to CN 220 that includes networkelements to provide various functions to support data andtelecommunications services to customers/subscribers (for example, usersof UE 202). The components of the CN 220 may be implemented in onephysical node or separate physical nodes. In some embodiments, NFV maybe utilized to virtualize any or all of the functions provided by thenetwork elements of the CN 220 onto physical compute/storage resourcesin servers, switches, etc. A logical instantiation of the CN 220 may bereferred to as a network slice, and a logical instantiation of a portionof the CN 220 may be referred to as a network sub-slice.

In some embodiments, the CN 220 may be an LTE CN 222, which may also bereferred to as an EPC. The LTE CN 222 may include MME 224, SGW 226, SGSN228, HSS 230, PGW 232, and PCRF 234 coupled with one another overinterfaces (or “reference points”) as shown. Functions of the elementsof the LTE CN 222 may be briefly introduced as follows.

The MME 224 may implement mobility management functions to track acurrent location of the UE 202 to facilitate paging, beareractivation/deactivation, handovers, gateway selection, authentication,etc.

The SGW 226 may terminate an Si interface toward the RAN and route datapackets between the RAN and the LTE CN 222. The SGW 226 may be a localmobility anchor point for inter-RAN node handovers and also may providean anchor for inter-3GPP mobility. Other responsibilities may includelawful intercept, charging, and some policy enforcement.

The SGSN 228 may track a location of the UE 202 and perform securityfunctions and access control. In addition, the SGSN 228 may performinter-EPC node signaling for mobility between different RAT networks;PDN and S-GW selection as specified by MME 224; MME selection forhandovers; etc. The S3 reference point between the MME 224 and the SGSN228 may enable user and bearer information exchange for inter-3GPPaccess network mobility in idle/active states.

The HSS 230 may include a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The HSS 230 can provide support forrouting/roaming, authentication, authorization, naming/addressingresolution, location dependencies, etc. An S6a reference point betweenthe HSS 230 and the MME 224 may enable transfer of subscription andauthentication data for authenticating/authorizing user access to theLTE CN 220.

The PGW 232 may terminate an SGi interface toward a data network (DN)236 that may include an application/content server 238. The PGW 232 mayroute data packets between the LTE CN 222 and the data network 236. ThePGW 232 may be coupled with the SGW 226 by an S5 reference point tofacilitate user plane tunneling and tunnel management. The PGW 232 mayfurther include a node for policy enforcement and charging datacollection (for example, PCEF). Additionally, the SGi reference pointbetween the PGW 232 and the data network 2 36 may be an operatorexternal public, a private PDN, or an intra-operator packet datanetwork, for example, for provision of IMS services. The PGW 232 may becoupled with a PCRF 234 via a Gx reference point.

The PCRF 234 is the policy and charging control element of the LTE CN222. The PCRF 234 may be communicatively coupled to the app/contentserver 238 to determine appropriate QoS and charging parameters forservice flows. The PCRF 232 may provision associated rules into a PCEF(via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 220 may be a 5GC 240. The 5GC 240 mayinclude an AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF254, PCF 256, UDM 258, and AF 260 coupled with one another overinterfaces (or “reference points”) as shown. Functions of the elementsof the 5GC 240 may be briefly introduced as follows.

The AUSF 242 may store data for authentication of UE 202 and handleauthentication-related functionality. The AUSF 242 may facilitate acommon authentication framework for various access types. In addition tocommunicating with other elements of the 5GC 240 over reference pointsas shown, the AUSF 242 may exhibit an Nausf service-based interface.

The AMF 244 may allow other functions of the 5GC 240 to communicate withthe UE 202 and the RAN 204 and to subscribe to notifications aboutmobility events with respect to the UE 202. The AMF 244 may beresponsible for registration management (for example, for registering UE202), connection management, reachability management, mobilitymanagement, lawful interception of AMF-related events, and accessauthentication and authorization. The AMF 244 may provide transport forSM messages between the UE 202 and the SMF 246, and act as a transparentproxy for routing SM messages. AMF 244 may also provide transport forSMS messages between UE 202 and an SMSF. AMF 244 may interact with theAUSF 242 and the UE 202 to perform various security anchor and contextmanagement functions. Furthermore, AMF 244 may be a termination point ofa RAN CP interface, which may include or be an N2 reference pointbetween the RAN 204 and the AMF 244; and the AMF 244 may be atermination point of NAS (N1) signaling, and perform NAS ciphering andintegrity protection. AMF 244 may also support NAS signaling with the UE202 over an N3 IWF interface.

The SMF 246 may be responsible for SM (for example, sessionestablishment, tunnel management between UPF 248 and AN 208); UE IPaddress allocation and management (including optional authorization);selection and control of UP function; configuring traffic steering atUPF 248 to route traffic to proper destination; termination ofinterfaces toward policy control functions; controlling part of policyenforcement, charging, and QoS; lawful intercept (for SM events andinterface to LI system); termination of SM parts of NAS messages;downlink data notification; initiating AN specific SM information, sentvia AMF 244 over N2 to AN 208; and determining SSC mode of a session. SMmay refer to management of a PDU session, and a PDU session or “session”may refer to a PDU connectivity service that provides or enables theexchange of PDUs between the UE 202 and the data network 236.

The UPF 248 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to data network236, and a branching point to support multi-homed PDU session. The UPF248 may also perform packet routing and forwarding, perform packetinspection, enforce the user plane part of policy rules, lawfullyintercept packets (UP collection), perform traffic usage reporting,perform QoS handling for a user plane (e.g., packet filtering, gating,UL/DL rate enforcement), perform uplink traffic verification (e.g.,SDF-to-QoS flow mapping), transport level packet marking in the uplinkand downlink, and perform downlink packet buffering and downlink datanotification triggering. UPF 248 may include an uplink classifier tosupport routing traffic flows to a data network.

The NSSF 250 may select a set of network slice instances serving the UE202. The NSSF 250 may also determine allowed NSSAI and the mapping tothe subscribed S-NSSAIs, if needed. The NSSF 250 may also determine theAMF set to be used to serve the UE 202, or a list of candidate AMFsbased on a suitable configuration and possibly by querying the NRF 254.The selection of a set of network slice instances for the UE 202 may betriggered by the AMF 244 with which the UE 202 is registered byinteracting with the NSSF 250, which may lead to a change of AMF. TheNSSF 250 may interact with the AMF 244 via an N22 reference point; andmay communicate with another NSSF in a visited network via an N31reference point (not shown). Additionally, the NSSF 250 may exhibit anNnssf service-based interface.

The NEF 252 may securely expose services and capabilities provided by3GPP network functions for third party, internal exposure/re-exposure,AFs (e.g., AF 260), edge computing or fog computing systems, etc. Insuch embodiments, the NEF 252 may authenticate, authorize, or throttlethe AFs. NEF 252 may also translate information exchanged with the AF260 and information exchanged with internal network functions. Forexample, the NEF 252 may translate between an AF-Service-Identifier andan internal 5GC information. NEF 252 may also receive information fromother NFs based on exposed capabilities of other NFs. This informationmay be stored at the NEF 252 as structured data, or at a data storage NFusing standardized interfaces. The stored information can then bere-exposed by the NEF 252 to other NFs and AFs, or used for otherpurposes such as analytics. Additionally, the NEF 252 may exhibit anNnef service-based interface.

The NRF 254 may support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 254 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the like mayrefer to the creation of an instance, and an “instance” may refer to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code. Additionally, the NRF 254 may exhibit theNnrf service-based interface.

The PCF 256 may provide policy rules to control plane functions toenforce them, and may also support unified policy framework to governnetwork behavior. The PCF 256 may also implement a front end to accesssubscription information relevant for policy decisions in a UDR of theUDM 258. In addition to communicating with functions over referencepoints as shown, the PCF 256 exhibit an Npcf service-based interface.

The UDM 258 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 202. For example, subscription data may becommunicated via an N8 reference point between the UDM 258 and the AMF244. The UDM 258 may include two parts, an application front end and aUDR. The UDR may store subscription data and policy data for the UDM 258and the PCF 256, and/or structured data for exposure and applicationdata (including PFDs for application detection, application requestinformation for multiple UEs 202) for the NEF 252. The Nudrservice-based interface may be exhibited by the UDR 221 to allow the UDM258, PCF 256, and NEF 252 to access a particular set of the stored data,as well as to read, update (e.g., add, modify), delete, and subscribe tonotification of relevant data changes in the UDR. The UDM may include aUDM-FE, which is in charge of processing credentials, locationmanagement, subscription management and so on. Several different frontends may serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing, user identification handling,access authorization, registration/mobility management, and subscriptionmanagement. In addition to communicating with other NFs over referencepoints as shown, the UDM 258 may exhibit the Nudm service-basedinterface.

The AF 260 may provide application influence on traffic routing, provideaccess to NEF, and interact with the policy framework for policycontrol.

In some embodiments, the 5GC 240 may enable edge computing by selectingoperator/3rd party services to be geographically close to a point thatthe UE 202 is attached to the network. This may reduce latency and loadon the network. To provide edge-computing implementations, the 5GC 240may select a UPF 248 close to the UE 202 and execute traffic steeringfrom the UPF 248 to data network 236 via the N6 interface. This may bebased on the UE subscription data, UE location, and information providedby the AF 260. In this way, the AF 260 may influence UPF (re)selectionand traffic routing. Based on operator deployment, when AF 260 isconsidered to be a trusted entity, the network operator may permit AF260 to interact directly with relevant NFs. Additionally, the AF 260 mayexhibit an Naf service-based interface.

The data network 236 may represent various network operator services,Internet access, or third party services that may be provided by one ormore servers including, for example, application/content server 238.

FIG. 3 schematically illustrates a wireless network 300 in accordancewith various embodiments. The wireless network 300 may include a UE 302in wireless communication with an AN 304. The UE 302 and AN 304 may besimilar to, and substantially interchangeable with, like-namedcomponents described elsewhere herein.

The UE 302 may be communicatively coupled with the AN 304 via connection306. The connection 306 is illustrated as an air interface to enablecommunicative coupling, and can be consistent with cellularcommunications protocols such as an LTE protocol or a 5G NR protocoloperating at mmWave or sub-6 GHz frequencies.

The UE 302 may include a host platform 308 coupled with a modem platform310. The host platform 308 may include application processing circuitry312, which may be coupled with protocol processing circuitry 314 of themodem platform 310. The application processing circuitry 312 may runvarious applications for the UE 302 that source/sink application data.The application processing circuitry 312 may further implement one ormore layer operations to transmit/receive application data to/from adata network. These layer operations may include transport (for exampleUDP) and Internet (for example, IP) operations

The protocol processing circuitry 314 may implement one or more of layeroperations to facilitate transmission or reception of data over theconnection 306. The layer operations implemented by the protocolprocessing circuitry 314 may include, for example, MAC, RLC, PDCP, RRCand NAS operations.

The modem platform 310 may further include digital baseband circuitry316 that may implement one or more layer operations that are “below”layer operations performed by the protocol processing circuitry 314 in anetwork protocol stack. These operations may include, for example, PHYoperations including one or more of HARQ-ACK functions,scrambling/descrambling, encoding/decoding, layer mapping/de-mapping,modulation symbol mapping, received symbol/bit metric determination,multi-antenna port precoding/decoding, which may include one or more ofspace-time, space-frequency or spatial coding, reference signalgeneration/detection, preamble sequence generation and/or decoding,synchronization sequence generation/detection, control channel signalblind decoding, and other related functions.

The modem platform 310 may further include transmit circuitry 318,receive circuitry 320, RF circuitry 322, and RF front end (RFFE) 324,which may include or connect to one or more antenna panels 326. Briefly,the transmit circuitry 318 may include a digital-to-analog converter,mixer, intermediate frequency (IF) components, etc.; the receivecircuitry 320 may include an analog-to-digital converter, mixer, IFcomponents, etc.; the RF circuitry 322 may include a low-noiseamplifier, a power amplifier, power tracking components, etc.; RFFE 324may include filters (for example, surface/bulk acoustic wave filters),switches, antenna tuners, beamforming components (for example,phase-array antenna components), etc. The selection and arrangement ofthe components of the transmit circuitry 318, receive circuitry 320, RFcircuitry 322, RFFE 324, and antenna panels 326 (referred generically as“transmit/receive components”) may be specific to details of a specificimplementation such as, for example, whether communication is TDM orFDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, thetransmit/receive components may be arranged in multiple paralleltransmit/receive chains, may be disposed in the same or differentchips/modules, etc.

In some embodiments, the protocol processing circuitry 314 may includeone or more instances of control circuitry (not shown) to providecontrol functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 326,RFFE 324, RF circuitry 322, receive circuitry 320, digital basebandcircuitry 316, and protocol processing circuitry 314. In someembodiments, the antenna panels 326 may receive a transmission from theAN 304 by receive-beamforming signals received by a plurality ofantennas/antenna elements of the one or more antenna panels 326.

A UE transmission may be established by and via the protocol processingcircuitry 314, digital baseband circuitry 316, transmit circuitry 318,RF circuitry 322, RFFE 324, and antenna panels 326. In some embodiments,the transmit components of the UE 304 may apply a spatial filter to thedata to be transmitted to form a transmit beam emitted by the antennaelements of the antenna panels 326.

Similar to the UE 302, the AN 304 may include a host platform 328coupled with a modem platform 330. The host platform 328 may includeapplication processing circuitry 332 coupled with protocol processingcircuitry 334 of the modem platform 330. The modem platform may furtherinclude digital baseband circuitry 336, transmit circuitry 338, receivecircuitry 340, RF circuitry 342, RFFE circuitry 344, and antenna panels346. The components of the AN 304 may be similar to and substantiallyinterchangeable with like-named components of the UE 302. In addition toperforming data transmission/reception as described above, thecomponents of the AN 308 may perform various logical functions thatinclude, for example, RNC functions such as radio bearer management,uplink and downlink dynamic radio resource management, and data packetscheduling.

FIG. 4 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein. Specifically, FIG. 4 shows a diagrammaticrepresentation of hardware resources 400 including one or moreprocessors (or processor cores) 410, one or more memory/storage devices420, and one or more communication resources 430, each of which may becommunicatively coupled via a bus 440 or other interface circuitry. Forembodiments where node virtualization (e.g., NFV) is utilized, ahypervisor 402 may be executed to provide an execution environment forone or more network slices/sub-slices to utilize the hardware resources400.

The processors 410 may include, for example, a processor 412 and aprocessor 414. The processors 410 may be, for example, a centralprocessing unit (CPU), a reduced instruction set computing (RISC)processor, a complex instruction set computing (CISC) processor, agraphics processing unit (GPU), a DSP such as a baseband processor, anASIC, an FPGA, a radiofrequency integrated circuit (RFIC), anotherprocessor (including those discussed herein), or any suitablecombination thereof.

The memory/storage devices 420 may include main memory, disk storage, orany suitable combination thereof. The memory/storage devices 420 mayinclude, but are not limited to, any type of volatile, non-volatile, orsemi-volatile memory such as dynamic random access memory (DRAM), staticrandom access memory (SRAM), erasable programmable read-only memory(EPROM), electrically erasable programmable read-only memory (EEPROM),Flash memory, solid-state storage, etc.

The communication resources 430 may include interconnection or networkinterface controllers, components, or other suitable devices tocommunicate with one or more peripheral devices 404 or one or moredatabases 406 or other network elements via a network 408. For example,the communication resources 430 may include wired communicationcomponents (e.g., for coupling via USB, Ethernet, etc.), cellularcommunication components, NFC components, Bluetooth® (or Bluetooth® LowEnergy) components, Wi-Fi® components, and other communicationcomponents.

Instructions 450 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 410 to perform any one or more of the methodologies discussedherein. The instructions 450 may reside, completely or partially, withinat least one of the processors 410 (e.g., within the processor's cachememory), the memory/storage devices 420, or any suitable combinationthereof. Furthermore, any portion of the instructions 450 may betransferred to the hardware resources 400 from any combination of theperipheral devices 404 or the databases 406. Accordingly, the memory ofprocessors 410, the memory/storage devices 420, the peripheral devices404, and the databases 406 are examples of computer-readable andmachine-readable media.

For one or more embodiments, at least one of the components set forth inone or more of the preceding figures may be configured to perform one ormore operations, techniques, processes, and/or methods as set forth inthe example section below. For example, the baseband circuitry asdescribed above in connection with one or more of the preceding figuresmay be configured to operate in accordance with one or more of theexamples set forth below. For another example, circuitry associated witha UE, base station, network element, etc. as described above inconnection with one or more of the preceding figures may be configuredto operate in accordance with one or more of the examples set forthbelow in the example section.

In various embodiments, the devices/components of FIGS. 2-4, andparticularly the baseband circuitry of FIG. 3, may be used to practice,in whole or in part, any of the operation flow/algorithmic structuresdepicted in FIGS. 1A, 1B, and 1C.

One example of an operation flow/algorithmic structure is depicted inFIG. 1A. In this example, operation flow/algorithmic structure 100 mayinclude, at 105, retrieving configuration information associated withphysical downlink control channel (PDCCH) monitoring from multipletransmission reception points (TRPs) by a user equipment (UE) frommemory, wherein the configuration information includes an indication ofmultiple control resource sets (CORESETs) associated with a commontransmission configuration indicator (TCI) group. Operationflow/algorithmic structure 100 may further include, at 110, encoding amessage that includes the configuration information for transmission tothe UE.

Another example of an operation flow/algorithmic structure is depictedin FIG. 1B. In this example, operation flow/algorithmic structure 120may include, at 125, determining configuration information associatedwith physical downlink control channel (PDCCH) monitoring from multipletransmission reception points (TRPs) by a user equipment (UE), whereinthe configuration information includes an indication of multiple controlresource sets (CORESETs) associated with a common transmissionconfiguration indicator (TCI) group. Operation flow/algorithmicstructure 120 may further include, at 130, encoding a message thatincludes the configuration information for transmission to the UE.

Another example of an operation flow/algorithmic structure is depictedin FIG. 1C. In this example, operation flow/algorithmic structure 140may include, at 145, determining configuration information that includesan indication of a first pool index value of a control resource set(CORESET) and a second pool index value of the CORESET, wherein thefirst pool index value is different from the second pool index value.Operation flow/algorithmic structure 140 may further include, at 150,encoding a message that includes the configuration information fortransmission to a UE.

Examples

Example 1 may include a method of distinguishing UE behavior based onall TCI codepoints mapped to one TCI state, UE configuration withdifferent CORESETPoolIndex values, at least one TCI codepoint mapped totwo TCI states, TCI-group.

Example 2 may include the method of example 1 or some other exampleherein, wherein UE behavior comprises of setting PDSCH default beams.

Example 3 may include the method of example 1 or some other exampleherein, wherein UE behavior comprises of prioritizing PDCCH monitoring.

Example 4 may include a method comprising: determining an operation, theoperation to include a single TRP operation; a single DCI, multi-TRPoperation mode; or multi-DCI, multi-TRP operation; and determiningapplicability of PDCCH prioritization based on the determined operation.

Example 5 may include the method of example 4 some other example herein,wherein the operation comprises multi-DC, multi-TRP operation in saiddetermining applicability comprises determining PDCCH prioritization isnot applicable to the operation.

Example 6 may include the method of example 4 some other example herein,further comprising: determining whether a UE is configured with twodifferent values of CORESET Pool Index in Control Resource Set; anddetermining applicability of PDCCH prioritization based on saiddetermination of whether the UE is configured with the two differentvalues.

Example 7 may include a method comprising setting PDSCH default beambehavior for single TRP operation; single DCI, multi-TRP operation; andmulti-DCI, multi-TRP operation.

Example 8 may include a method comprising prioritizing PDCCH based onQCL-type D for multi-panel reception and a single-panel reception.

Example 9 may include a method comprising: determining whether a UE isconfigured with two different values of CORESET Pool Index in ControlResource Set; and monitoring PDCCH candidates and overlapping PDCCHmonitoring occasions in multiple CORESETS that are associated with asame value of CORESET Pool Index.

Example 10 may include a method of operating a UE, the method comprisingdetermining whether all TCI codepoints are mapped to a single TCI stateand a UE is not configured with two different values of CORESETPoolIndexin ControlResourceSet and an offset between reception of a DL DCI andcorresponding PDSCH is less than a threshold timeDurationForQCL; andassuming, based on said determining, that DM-RS ports of PDSCH of aserving cell are quasi co-located with the RS(s) with respect to the QCLparameter(s) used for PDCCH quasi co-location indication of the CORESETassociated with a monitored search space with a lowestcontrolResourceSetId in a latest slot in which one or more CORESETswithin an active BWP of the serving cell are monitored by the UE.

Example X1 includes an apparatus comprising: memory to storeconfiguration information associated with physical downlink controlchannel (PDCCH) monitoring from multiple transmission reception points(TRPs) by a user equipment (UE); and processor circuitry, coupled withthe memory, to: retrieve the configuration information from the memory,wherein the configuration information includes an indication of multiplecontrol resource sets (CORESETs) associated with a common transmissionconfiguration indicator (TCI) group; and encode a message that includesthe configuration information for transmission to the UE.

Example X2 includes the apparatus of example X1 or some other exampleherein, wherein the TCI group comprises TCI states associated with acommon reception panel.

Example X3 includes the apparatus of example X1 or some other exampleherein, wherein the TCI group includes TCI states in different cellsthat are associated with a common reception panel and have a common TCIstate identifier.

Example X4 includes the apparatus of example X1 or some other exampleherein, wherein the TCI group includes TCI states associated withCORESETs that are in turn associated with a common CORESET pool indexvalue and are associated with a common reception panel.

Example X5 includes the apparatus of example X1 or some other exampleherein, wherein the TCI group includes TCI states that are associatedwith a common value of a panel index and are associated with a commonreception panel.

Example X6 includes the apparatus of example X1 or some other exampleherein, wherein the TCI group includes two TCI states comprising achannel state information-reference signal indicator (CRI) or asynchronization signal block resource indicator (SSBRI) that arereported in a single reporting instance and are not associated with acommon reception panel.

Example X7 includes the apparatus of example X6 or some other exampleherein, wherein a first CRI or SSBRI is associated with a firstreception panel and a second CRI or SSBRI is associated with a secondreception panel.

Example X8 includes one or more non-transitory computer-readable mediastoring instructions that, when executed by one or more processors, areto cause a device to: determine configuration information associatedwith physical downlink control channel (PDCCH) monitoring from multipletransmission reception points (TRPs) by a user equipment (UE), whereinthe configuration information includes an indication of multiple controlresource sets (CORESETs) associated with a common transmissionconfiguration indicator (TCI) group; and encode a message that includesthe configuration information for transmission to the UE.

Example X9 includes the one or more non-transitory computer-readablemedia of example X8 or some other example herein, wherein the TCI groupcomprises TCI states associated with a common reception panel.

Example X10 includes the one or more non-transitory computer-readablemedia of example X8 or some other example herein, wherein the TCI groupincludes TCI states in different cells that are associated with a commonreception panel and have a common TCI state identifier.

Example X11 includes the one or more non-transitory computer-readablemedia of example X8 or some other example herein, wherein the TCI groupincludes TCI states associated with CORESETs that are in turn associatedwith a common CORESET pool index value and are associated with a commonreception panel.

Example X12 includes the one or more non-transitory computer-readablemedia of example X8 or some other example herein, wherein the TCI groupincludes TCI states that are associated with a common value of a panelindex and are associated with a common reception panel.

Example X13 includes the one or more non-transitory computer-readablemedia of example X8 or some other example herein, wherein the TCI groupincludes two TCI states comprising a channel state information-referencesignal indicator (CRI) or a synchronization signal block resourceindicator (SSBRI) that are reported in a single reporting instance andare not associated with a common reception panel.

Example X14 includes the one or more non-transitory computer-readablemedia of example X13 or some other example herein, wherein a first CRIor SSBRI is associated with a first reception panel and a second CRI orSSBRI is associated with a second reception panel.

Example X15 includes one or more non-transitory computer-readable mediastoring instructions that, when executed by one or more processors, areto cause a device to: determine configuration information that includesan indication of a first pool index value of a control resource set(CORESET) and a second pool index value of the CORESET, wherein thefirst pool index value is different from the second pool index value;and encode a message for transmission to a UE that includes theconfiguration information.

Example X16 includes the one or more non-transitory computer-readablemedia of example X15 or some other example herein, wherein theconfiguration information is further to configure the UE for operationwith carrier aggregation in common frequency band.

Example Z01 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examples1-X16, or any other method or process described herein.

Example Z02 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of examples 1-X16, or any other method or processdescribed herein.

Example Z03 may include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of examples 1-X16, or any other method or processdescribed herein.

Example Z04 may include a method, technique, or process as described inor related to any of examples 1-X16, or portions or parts thereof.

Example Z05 may include an apparatus comprising: one or more processorsand one or more computer-readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of examples 1-X16, or portions thereof.

Example Z06 may include a signal as described in or related to any ofexamples 1-10, or portions or parts thereof.

Example Z07 may include a datagram, packet, frame, segment, protocoldata unit (PDU), or message as described in or related to any ofexamples 1-X16, or portions or parts thereof, or otherwise described inthe present disclosure.

Example Z08 may include a signal encoded with data as described in orrelated to any of examples 1-X16, or portions or parts thereof, orotherwise described in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame,segment, protocol data unit (PDU), or message as described in or relatedto any of examples 1-X16, or portions or parts thereof, or otherwisedescribed in the present disclosure.

Example Z10 may include an electromagnetic signal carryingcomputer-readable instructions, wherein execution of thecomputer-readable instructions by one or more processors is to cause theone or more processors to perform the method, techniques, or process asdescribed in or related to any of examples 1-X16, or portions thereof.

Example Z11 may include a computer program comprising instructions,wherein execution of the program by a processing element is to cause theprocessing element to carry out the method, techniques, or process asdescribed in or related to any of examples 1-X16, or portions thereof.

Example Z12 may include a signal in a wireless network as shown anddescribed herein.

Example Z13 may include a method of communicating in a wireless networkas shown and described herein.

Example Z14 may include a system for providing wireless communication asshown and described herein.

Example Z15 may include a device for providing wireless communication asshown and described herein.

Any of the above-described examples may be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of various embodiments.

Abbreviations

Unless used differently herein, terms, definitions, and abbreviationsmay be consistent with terms, definitions, and abbreviations defined in3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of the presentdocument, the following abbreviations may apply to the examples andembodiments discussed herein.

3GPP Third Generation Partnership Project 4G Fourth Generation 5G FifthGeneration 5GC 5G Core network ACK Acknowledgement AF ApplicationFunction AM Acknowledged Mode AMBR Aggregate Maximum Bit Rate AMF Accessand Mobility Management Function AN Access Network ANR AutomaticNeighbour Relation AP Application Protocol, Antenna Port, Access PointAPI Application Programming Interface APN Access Point Name ARPAllocation and Retention Priority ARQ Automatic Repeat Request AS AccessStratum ASN.1 Abstract Syntax Notation One AUSF Authentication ServerFunction AWGN Additive White Gaussian Noise BAP Backhaul AdaptationProtocol BCH Broadcast Channel BER Bit Error Ratio BFD Beam FailureDetection BLER Block Error Rate BPSK Binary Phase Shift Keying BRASBroadband Remote Access Server BSS Business Support System BS BaseStation BSR Buffer Status Report BW Bandwidth BWP Bandwidth Part C-RNTICell Radio Network Temporary Identity CA Carrier Aggregation,Certification Authority CAPEX CAPital EXpenditure CBRA Contention BasedRandom Access CC Component Carrier, Country Code, Cryptographic ChecksumCCA Clear Channel Assessment CCE Control Channel Element CCCH CommonControl Channel CE Coverage Enhancement CDM Content Delivery NetworkCDMA Code-Division Multiple Access CFRA Contention Free Random Access CGCell Group CI Cell Identity CID Cell-ID (e.g., positioning method) CIMCommon Information Model CIR Carrier to Interference Ratio CK Cipher KeyCM Connection Management, Conditional Mandatory CMAS Commercial MobileAlert Service CMD Command CMS Cloud Management System CO ConditionalOptional CoMP Coordinated Multi-Point CORESET Control Resource Set COTSCommercial Off-The-Shelf CP Control Plane, Cyclic Prefix, ConnectionPoint CPD Connection Point Descriptor CPE Customer Premise EquipmentCPICH Common Pilot Channel CQI Channel Quality Indicator CPU CSIprocessing unit, Central Processing Unit C/R Command/Response field bitCRAN Cloud Radio Access Network, Cloud RAN CRB Common Resource Block CRCCyclic Redundancy Check CRI Channel-State Information ResourceIndicator, CSI-RS Resource Indicator C-RNTI Cell RNTI CS CircuitSwitched CSAR Cloud Service Archive CSI Channel-State Information CSI-IMCSI Interference Measurement CSI-RS CSI Reference Signal CSI-RSRP CSIreference signal received power CSI-RSRQ CSI reference signal receivedquality CSI-SINR CSI signal-to-noise and interference ratio CSMA CarrierSense Multiple Access CSMA/CA CSMA with collision avoidance CSS CommonSearch Space, Cell-specific Search Space CTS Clear-to-Send CW CodewordCWS Contention Window Size D2D Device-to-Device DC Dual Connectivity,Direct Current DCI Downlink Control Information DF Deployment Flavour DLDownlink DMTF Distributed Management Task Force DPDK Data PlaneDevelopment Kit DM-RS, DMRS Demodulation Reference Signal DN Datanetwork DRB Data Radio Bearer DRS Discovery Reference Signal DRXDiscontinuous Reception DSL Domain Specific Language. Digital SubscriberLine DSLAM DSL Access Multiplexer DwPTS Downlink Pilot Time Slot E-LANEthernet Local Area Network E2E End-to-End ECCA extended clear channelassessment, extended CCA ECCE Enhanced Control Channel Element, EnhancedCCE ED Energy Detection EDGE Enhanced Datarates for GSM Evolution (GSMEvolution) EGMF Exposure Governance Management Function EGPRS EnhancedGPRS EIR Equipment Identity Register eLAA enhanced Licensed AssistedAccess, enhanced LAA EM Element Manager eMBB Enhanced Mobile BroadbandEMS Element Management System eNB evolved NodeB, E-UTRAN Node B EN-DCE-UTRA-NR Dual Connectivity EPC Evolved Packet Core EPDCCH enhancedPDCCH, enhanced Physical Downlink Control Cannel EPRE Energy perresource element EPS Evolved Packet System EREG enhanced REG, enhancedresource element groups ETSI European Telecommunications StandardsInstitute ETWS Earthquake and Tsunami Warning System eUICC embeddedUICC, embedded Universal Integrated Circuit Card E-UTRA Evolved UTRAE-UTRAN Evolved UTRAN EV2X Enhanced V2X F1AP F1 Application ProtocolF1-C F1 Control plane interface F1-U F1 User plane interface FACCH FastAssociated Control CHannel FACCH/F Fast Associated Control Channel/Fullrate FACCH/H Fast Associated Control Channel/Half rate FACH ForwardAccess Channel FAUSCH Fast Uplink Signalling Channel FB Functional BlockFBI Feedback Information FCC Federal Communications Commission FCCHFrequency Correction CHannel FDD Frequency Division Duplex FDM FrequencyDivision Multiplex FDMA Frequency Division Multiple Access FE Front EndFEC Forward Error Correction FFS For Further Study FFT Fast FourierTransformation feLAA further enhanced Licensed Assisted Access, furtherenhanced LAA FN Frame Number FPGA Field-Programmable Gate Array FRFrequency Range G-RNTI GERAN Radio Network Temporary Identity GERAN GSMEDGE RAN, GSM EDGE Radio Access Network GGSN Gateway GPRS Support NodeGLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: GlobalNavigation Satellite System) gNB Next Generation NodeB gNB-CUgNB-centralized unit, Next Generation NodeB centralized unit gNB-DUgNB-distributed unit, Next Generation NodeB distributed unit GNSS GlobalNavigation Satellite System GPRS General Packet Radio Service GSM GlobalSystem for Mobile Communications, Groupe Spécial Mobile GTP GPRSTunneling Protocol GTP-UGPRS Tunnelling Protocol for User Plane GTS GoTo Sleep Signal (related to WUS) GUMMEI Globally Unique MME IdentifierGUTI Globally Unique Temporary UE Identity HARQ Hybrid ARQ, HybridAutomatic Repeat Request HANDO Handover HFN HyperFrame Number HHO HardHandover HLR Home Location Register HN Home Network HO Handover HPLMNHome Public Land Mobile Network HSDPA High Speed Downlink Packet AccessHSN Hopping Sequence Number HSPA High Speed Packet Access HSS HomeSubscriber Server HSUPA High Speed Uplink Packet Access HTTP Hyper TextTransfer Protocol HTTPS Hyper Text Transfer Protocol Secure (https ishttp/1.1 over SSL, i.e. port 443) I-Block Information Block ICCIDIntegrated Circuit Card Identification IAB Integrated Access andBackhaul ICIC Inter-Cell Interference Coordination ID Identity,identifier IDFT Inverse Discrete Fourier Transform IE Informationelement IBE In-Band Emission IEEE Institute of Electrical andElectronics Engineers IEI Information Element Identifier IEIDLInformation Element Identifier Data Length IETF Internet EngineeringTask Force IF Infrastructure IM Interference Measurement,Intermodulation, IP Multimedia IMC IMS Credentials IMEI InternationalMobile Equipment Identity IMGI International mobile group identity IMPIIP Multimedia Private Identity IMPU IP Multimedia PUblic identity IMS IPMultimedia Subsystem IMSI International Mobile Subscriber Identity IoTInternet of Things IP Internet Protocol Ipsec IP Security, InternetProtocol Security IP-CAN IP-Connectivity Access Network IP-M IPMulticast IPv4 Internet Protocol Version 4 IPv6 Internet ProtocolVersion 6 IR Infrared IS In Sync IRP Integration Reference Point ISDNIntegrated Services Digital Network ISIM IM Services Identity Module ISOInternational Organisation for Standardisation ISP Internet ServiceProvider IWF Interworking-Function I-WLAN Interworking WLAN Constraintlength of the convolutional code, USIM Individual key kB Kilobyte (1000bytes) kbps kilo-bits per second Kc Ciphering key Ki Individualsubscriber authentication key KPI Key Performance Indicator KQI KeyQuality Indicator KSI Key Set Identifier ksps kilo-symbols per secondKVM Kernel Virtual Machine L1 Layer 1 (physical layer) L1-RSRP Layer 1reference signal received power L2 Layer 2 (data link layer) L3 Layer 3(network layer) LAA Licensed Assisted Access LAN Local Area Network LBTListen Before Talk LCM LifeCycle Management LCR Low Chip Rate LCSLocation Services LCID Logical Channel ID LI Layer Indicator LLC LogicalLink Control, Low Layer Compatibility LPLMN Local PLMN LPP LTEPositioning Protocol LSB Least Significant Bit LTE Long Term EvolutionLWA LTE-WLAN aggregation LWIP LTE/WLAN Radio Level Integration withIPsec Tunnel LTE Long Term Evolution M2M Machine-to-Machine MAC MediumAccess Control (protocol layering context) MAC Message authenticationcode (security/encryption context) MAC-A MAC used for authentication andkey agreement (TSG T WG3 context) MAC-IMAC used for data integrity ofsignalling messages (TSG T WG3 context) MANO Management andOrchestration MBMS Multimedia Broadcast and Multicast Service MBSFNMultimedia Broadcast multicast service Single Frequency Network MCCMobile Country Code MCG Master Cell Group MCOT Maximum Channel OccupancyTime MCS Modulation and coding scheme MDAF Management Data AnalyticsFunction MDAS Management Data Analytics Service MDT Minimization ofDrive Tests ME Mobile Equipment MeNB master eNB MER Message Error RatioMGL Measurement Gap Length MGRP Measurement Gap Repetition Period MIBMaster Information Block, Management Information Base MIMO MultipleInput Multiple Output MLC Mobile Location Centre MM Mobility ManagementMME Mobility Management Entity MN Master Node MO Measurement Object,Mobile Originated MPBCH MTC Physical Broadcast CHannel MPDCCH MTCPhysical Downlink Control CHannel MPDSCH MTC Physical Downlink SharedCHannel MPRACH MTC Physical Random Access CHannel MPUSCH MTC PhysicalUplink Shared Channel MPLS MultiProtocol Label Switching MS MobileStation MSB Most Significant Bit MSC Mobile Switching Centre MSI MinimumSystem Information, MCH Scheduling Information MSID Mobile StationIdentifier MSIN Mobile Station Identification Number MSISDN MobileSubscriber ISDN Number MT Mobile Terminated, Mobile Termination MTCMachine-Type Communications mMTC massive MTC, massive Machine-TypeCommunications MU-MIMO Multi User MIMO MWUS MTC wake-up signal, MTC WUSNACK Negative Acknowledgement NAI Network Access Identifier NASNon-Access Stratum, Non-Access Stratum layer NCT Network ConnectivityTopology NC-JT Non-Coherent Joint Transmission NEC Network CapabilityExposure NE-DC NR-E-UTRA Dual Connectivity NEF Network Exposure FunctionNF Network Function NFP Network Forwarding Path NFPD Network ForwardingPath Descriptor NFV Network Functions Virtualization NFVI NFVInfrastructure NFVO NFV Orchestrator NG Next Generation, Next GenNGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NM Network Manager NMSNetwork Management System N-PoP Network Point of Presence NMIB, N-MIBNarrowband MIB NPBCH Narrowband Physical Broadcast CHannel NPDCCHNarrowband Physical Downlink Control CHannel NPDSCH Narrowband PhysicalDownlink Shared CHannel NPRACH Narrowband Physical Random Access CHannelNPUSCH Narrowband Physical Uplink Shared CHannel NPSS Narrowband PrimarySynchronization Signal NSSS Narrowband Secondary Synchronization SignalNR New Radio, Neighbour Relation NRF NF Repository Function NRSNarrowband Reference Signal NS Network Service NSA Non-Standaloneoperation mode NSD Network Service Descriptor NSR Network Service RecordNSSAI Network Slice Selection Assistance Information S-NNSAISingle-NSSAI NSSF Network Slice Selection Function NW Network NWUSNarrowband wake-up signal, Narrowband WUS NZP Non-Zero Power O&MOperation and Maintenance ODU2 Optical channel Data Unit - type 2 OFDMOrthogonal Frequency Division Multiplexing OFDMA Orthogonal FrequencyDivision Multiple Access OOB Out-of-band OOS Out of Sync OPEX OPeratingEXpense OSI Other System Information OSS Operations Support System OTAover-the-air PAPR Peak-to-Average Power Ratio PAR Peak to Average RatioPBCH Physical Broadcast Channel PC Power Control, Personal Computer PCCPrimary Component Carrier, Primary CC PCell Primary Cell PCI PhysicalCell ID, Physical Cell Identity PCEF Policy and Charging EnforcementFunction PCF Policy Control Function PCRF Policy Control and ChargingRules Function PDCP Packet Data Convergence Protocol, Packet DataConvergence Protocol layer PDCCH Physical Downlink Control Channel PDCPPacket Data Convergence Protocol PDN Packet Data Network, Public DataNetwork PDSCH Physical Downlink Shared Channel PDU Protocol Data UnitPEI Permanent Equipment Identifiers PFD Packet Flow Description P-GW PDNGateway PHICH Physical hybrid-ARQ indicator channel PHY Physical layerPLMN Public Land Mobile Network PIN Personal Identification Number PMPerformance Measurement PMI Precoding Matrix Indicator PNF PhysicalNetwork Function PNFD Physical Network Function Descriptor PNFR PhysicalNetwork Function Record POC PTT over Cellular PP, PTP Point-to-Point PPPPoint-to-Point Protocol PRACH Physical RACH PRB Physical resource blockPRG Physical resource block group ProSe Proximity Services,Proximity-Based Service PRS Positioning Reference Signal PRR PacketReception Radio PS Packet Services PSBCH Physical Sidelink BroadcastChannel PSDCH Physical Sidelink Downlink Channel PSCCH Physical SidelinkControl Channel PSSCH Physical Sidelink Shared Channel PSCell PrimarySCell PSS Primary Synchronization Signal PSTN Public Switched TelephoneNetwork PT-RS Phase-tracking reference signal PTT Push-to-Talk PUCCHPhysical Uplink Control Channel PUSCH Physical Uplink Shared Channel QAMQuadrature Amplitude Modulation QCI QoS class of identifier QCL Quasico-location QFI QoS Flow ID, QoS Flow Identifier QoS Quality of ServiceQPSK Quadrature (Quaternary) Phase Shift Keying QZSS Quasi-ZenithSatellite System RA-RNTI Random Access RNTI RAB Radio Access Bearer,Random Access Burst RACH Random Access Channel RADIUS RemoteAuthentication Dial In User Service RAN Radio Access Network RAND RANDomnumber (used for authentication) RAR Random Access Response RAT RadioAccess Technology RAU Routing Area Update RB Resource block, RadioBearer RBG Resource block group REG Resource Element Group Rel ReleaseREQ REQuest RF Radio Frequency RI Rank Indicator RIV Resource indicatorvalue RL Radio Link RLC Radio Link Control, Radio Link Control layer RLCAM RLC Acknowledged Mode RLC UM RLC Unacknowledged Mode RLF Radio LinkFailure RLM Radio Link Monitoring RLM-RS Reference Signal for RLM RMRegistration Management RMC Reference Measurement Channel RMSI RemainingMSI, Remaining Minimum System Information RN Relay Node RNC RadioNetwork Controller RNL Radio Network Layer RNTI Radio Network TemporaryIdentifier ROHC RObust Header Compression RRC Radio Resource Control,Radio Resource Control layer RRM Radio Resource Management RS ReferenceSignal RSRP Reference Signal Received Power RSRQ Reference SignalReceived Quality RSSI Received Signal Strength Indicator RSU Road SideUnit RSTD Reference Signal Time difference RTP Real Time Protocol RTSReady-To-Send RTT Round Trip Time Rx Reception, Receiving, Receiver S1APS1 Application Protocol S1-MME S1 for the control plane S1-U S1 for theuser plane S-GW Serving Gateway S-RNTI SRNC Radio Network TemporaryIdentity S-TMSI SAE Temporary Mobile Station Identifier SA Standaloneoperation mode SAE System Architecture Evolution SAP Service AccessPoint SAPD Service Access Point Descriptor SAPI Service Access PointIdentifier SCC Secondary Component Carrier, Secondary CC SCell SecondaryCell SC-FDMA Single Carrier Frequency Division Multiple Access SCGSecondary Cell Group SCM Security Context Management SCS SubcarrierSpacing SCTP Stream Control Transmission Protocol SDAP Service DataAdaptation Protocol, Service Data Adaptation Protocol layer SDLSupplementary Downlink SDNF Structured Data Storage Network Function SDPSession Description Protocol SDSF Structured Data Storage Function SDUService Data Unit SEAF Security Anchor Function SeNB secondary eNB SEPPSecurity Edge Protection Proxy SFI Slot format indication SFTDSpace-Frequency Time Diversity, SFN and frame timing difference SFNSystem Frame Number SgNB Secondary gNB SGSN Serving GPRS Support NodeS-GW Serving Gateway SI System Information SI-RNTI System InformationRNTI SIB System Information Block SIM Subscriber Identity Module SIPSession Initiated Protocol SiP System in Package SL Sidelink SLA ServiceLevel Agreement SM Session Management SMF Session Management FunctionSMS Short Message Service SMSF SMS Function SMTC SSB-based MeasurementTiming Configuration SN Secondary Node, Sequence Number SoC System onChip SON Self-Organizing Network SpCell Special Cell SP-CSI-RNTISemi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQN Sequencenumber SR Scheduling Request SRB Signalling Radio Bearer SRS SoundingReference Signal SS Synchronization Signal SSB Synchronization SignalBlock, SS/PBCH Block SSBRI SS/PBCH Block Resource Indicator,Synchronization Signal Block Resource Indicator SSC Session and ServiceContinuity SS-RSRP Synchronization Signal based Reference SignalReceived Power SS-RSRQ Synchronization Signal based Reference SignalReceived Quality SS-SINR Synchronization Signal based Signal to Noiseand Interference Ratio SSS Secondary Synchronization Signal SSSG SearchSpace Set Group SSSIF Search Space Set Indicator SST Slice/Service TypesSU-MIMO Single User MIMO SUL Supplementary Uplink TA Timing Advance,Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAUTracking Area Update TB Transport Block TBS Transport Block Size TBD ToBe Defined TCI Transmission Configuration Indicator TCP TransmissionCommunication Protocol TDD Time Division Duplex TDM Time DivisionMultiplexing TDMA Time Division Multiple Access TE Terminal EquipmentTEID Tunnel End Point Identifier TFT Traffic Flow Template TMSITemporary Mobile Subscriber Identity TNL Transport Network Layer TPCTransmit Power Control TPMI Transmitted Precoding Matrix Indicator TRTechnical Report TRP, TRxP Transmission Reception Point TRS TrackingReference Signal TRx Transceiver TS Technical Specifications, TechnicalStandard TTI Transmission Time Interval Tx Transmission, Transmitting,Transmitter U-RNTI UTRAN Radio Network Temporary Identity UART UniversalAsynchronous Receiver and Transmitter UCI Uplink Control Information UEUser Equipment UDM Unified Data Management UDP User Datagram ProtocolUDSF Unstructured Data Storage Network Function UICC UniversalIntegrated Circuit Card UL Uplink UM Unacknowledged Mode UML UnifiedModelling Language UMTS Universal Mobile Telecommunications System UPUser Plane UPF User Plane Function URI Uniform Resource Identifier URLUniform Resource Locator URLLC Ultra- Reliable and Low Latency USBUniversal Serial Bus USIM Universal Subscriber Identity Module USSUE-specific search space UTRA UMTS Terrestrial Radio Access UTRANUniversal Terrestrial Radio Access Network UwPTS Uplink Pilot Time SlotV2I Vehicle-to-Infrastruction V2P Vehicle-to-Pedestrian V2VVehicle-to-Vehicle V2X Vehicle-to-everything VIM VirtualizedInfrastructure Manager VL Virtual Link, VLAN Virtual LAN, Virtual LocalArea Network VM Virtual Machine VNF Virtualized Network Function VNFFGVNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNFManager VoIP Voice-over-IP, Voice-over-Internet Protocol VPLMN VisitedPublic Land Mobile Network VPN Virtual Private Network VRB VirtualResource Block WiMAX Worldwide Interoperability for Microwave AccessWLAN Wireless Local Area Network WMAN Wireless Metropolitan Area NetworkWPAN Wireless Personal Area Network X2-C X2-Control plane X2-U X2-Userplane XML eXtensible Markup Language 8ES EXpected user RESponse XOReXclusive OR ZC Zadoff-Chu ZP Zero Power

Terminology

For the purposes of the present document, the following terms anddefinitions are applicable to the examples and embodiments discussedherein.

The term “circuitry” as used herein refers to, is part of, or includeshardware components such as an electronic circuit, a logic circuit, aprocessor (shared, dedicated, or group) and/or memory (shared,dedicated, or group), an Application Specific Integrated Circuit (ASIC),a field-programmable device (FPD) (e.g., a field-programmable gate array(FPGA), a programmable logic device (PLD), a complex PLD (CPLD), ahigh-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC),digital signal processors (DSPs), etc., that are configured to providethe described functionality. In some embodiments, the circuitry mayexecute one or more software or firmware programs to provide at leastsome of the described functionality. The term “circuitry” may also referto a combination of one or more hardware elements (or a combination ofcircuits used in an electrical or electronic system) with the programcode used to carry out the functionality of that program code. In theseembodiments, the combination of hardware elements and program code maybe referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, orincludes circuitry capable of sequentially and automatically carryingout a sequence of arithmetic or logical operations, or recording,storing, and/or transferring digital data. Processing circuitry mayinclude one or more processing cores to execute instructions and one ormore memory structures to store program and data information. The term“processor circuitry” may refer to one or more application processors,one or more baseband processors, a physical central processing unit(CPU), a single-core processor, a dual-core processor, a triple-coreprocessor, a quad-core processor, and/or any other device capable ofexecuting or otherwise operating computer-executable instructions, suchas program code, software modules, and/or functional processes.Processing circuitry may include more hardware accelerators, which maybe microprocessors, programmable processing devices, or the like. Theone or more hardware accelerators may include, for example, computervision (CV) and/or deep learning (DL) accelerators. The terms“application circuitry” and/or “baseband circuitry” may be consideredsynonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, orincludes circuitry that enables the exchange of information between twoor more components or devices. The term “interface circuitry” may referto one or more hardware interfaces, for example, buses, I/O interfaces,peripheral component interfaces, network interface cards, and/or thelike.

The term “user equipment” or “UE” as used herein refers to a device withradio communication capabilities and may describe a remote user ofnetwork resources in a communications network. The term “user equipment”or “UE” may be considered synonymous to, and may be referred to as,client, mobile, mobile device, mobile terminal, user terminal, mobileunit, mobile station, mobile user, subscriber, user, remote station,access agent, user agent, receiver, radio equipment, reconfigurableradio equipment, reconfigurable mobile device, etc. Furthermore, theterm “user equipment” or “UE” may include any type of wireless/wireddevice or any computing device including a wireless communicationsinterface.

The term “network element” as used herein refers to physical orvirtualized equipment and/or infrastructure used to provide wired orwireless communication network services. The term “network element” maybe considered synonymous to and/or referred to as a networked computer,networking hardware, network equipment, network node, router, switch,hub, bridge, radio network controller, RAN device, RAN node, gateway,server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any typeinterconnected electronic devices, computer devices, or componentsthereof. Additionally, the term “computer system” and/or “system” mayrefer to various components of a computer that are communicativelycoupled with one another. Furthermore, the term “computer system” and/or“system” may refer to multiple computer devices and/or multiplecomputing systems that are communicatively coupled with one another andconfigured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used hereinrefers to a computer device or computer system with program code (e.g.,software or firmware) that is specifically designed to provide aspecific computing resource. A “virtual appliance” is a virtual machineimage to be implemented by a hypervisor-equipped device that virtualizesor emulates a computer appliance or otherwise is dedicated to provide aspecific computing resource.

The term “resource” as used herein refers to a physical or virtualdevice, a physical or virtual component within a computing environment,and/or a physical or virtual component within a particular device, suchas computer devices, mechanical devices, memory space, processor/CPUtime, processor/CPU usage, processor and accelerator loads, hardwaretime or usage, electrical power, input/output operations, ports ornetwork sockets, channel/link allocation, throughput, memory usage,storage, network, database and applications, workload units, and/or thelike. A “hardware resource” may refer to compute, storage, and/ornetwork resources provided by physical hardware element(s). A“virtualized resource” may refer to compute, storage, and/or networkresources provided by virtualization infrastructure to an application,device, system, etc. The term “network resource” or “communicationresource” may refer to resources that are accessible by computerdevices/systems via a communications network. The term “systemresources” may refer to any kind of shared entities to provide services,and may include computing and/or network resources. System resources maybe considered as a set of coherent functions, network data objects orservices, accessible through a server where such system resources resideon a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium,either tangible or intangible, which is used to communicate data or adata stream. The term “channel” may be synonymous with and/or equivalentto “communications channel,” “data communications channel,”“transmission channel,” “data transmission channel,” “access channel,”“data access channel,” “link,” “data link,” “carrier,” “radiofrequencycarrier,” and/or any other like term denoting a pathway or mediumthrough which data is communicated. Additionally, the term “link” asused herein refers to a connection between two devices through a RAT forthe purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used hereinrefers to the creation of an instance. An “instance” also refers to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code.

The terms “coupled,” “communicatively coupled,” along with derivativesthereof are used herein. The term “coupled” may mean two or moreelements are in direct physical or electrical contact with one another,may mean that two or more elements indirectly contact each other butstill cooperate or interact with each other, and/or may mean that one ormore other elements are coupled or connected between the elements thatare said to be coupled with each other. The term “directly coupled” maymean that two or more elements are in direct contact with one another.The term “communicatively coupled” may mean that two or more elementsmay be in contact with one another by a means of communication includingthrough a wire or other interconnect connection, through a wirelesscommunication channel or link, and/or the like.

The term “information element” refers to a structural element containingone or more fields. The term “field” refers to individual contents of aninformation element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configurationconfigured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block.

The term “a “Primary Cell” refers to the MCG cell, operating on theprimary frequency, in which the UE either performs the initialconnection establishment procedure or initiates the connectionre-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UEperforms random access when performing the Reconfiguration with Syncprocedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radioresources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cellscomprising the PSCell and zero or more secondary cells for a UEconfigured with DC.

The term “Serving Cell” refers to the primary cell for a UE in RRCCONNECTED not configured with CA/DC there is only one serving cellcomprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cellscomprising the Special Cell(s) and all secondary cells for a UE in RRCCONNECTED configured with CA/.

The term “Special Cell” refers to the PCell of the MCG or the PSCell ofthe SCG for DC operation; otherwise, the term “Special Cell” refers tothe Pcell.

What is claimed is:
 1. An apparatus comprising: memory to storeconfiguration information associated with physical downlink controlchannel (PDCCH) monitoring from multiple transmission reception points(TRPs) by a user equipment (UE); and processor circuitry, coupled withthe memory, to: retrieve the configuration information from the memory,wherein the configuration information includes an indication of multiplecontrol resource sets (CORESETs) associated with a common transmissionconfiguration indicator (TCI) group; and encode a message that includesthe configuration information for transmission to the UE.
 2. Theapparatus of claim 1, wherein the TCI group comprises TCI statesassociated with a common reception panel.
 3. The apparatus of claim 1,wherein the TCI group includes TCI states in different cells that areassociated with a common reception panel and have a common TCI stateidentifier.
 4. The apparatus of claim 1, wherein the TCI group includesTCI states associated with CORESETs that are in turn associated with acommon CORESET pool index value and are associated with a commonreception panel.
 5. The apparatus of claim 1, wherein the TCI groupincludes TCI states that are associated with a common value of a panelindex and are associated with a common reception panel.
 6. The apparatusof claim 1, wherein the TCI group includes two TCI states comprising achannel state information-reference signal indicator (CRI) or asynchronization signal block resource indicator (SSBRI) that arereported in a single reporting instance and are not associated with acommon reception panel.
 7. The apparatus of claim 6, wherein a first CRIor SSBRI is associated with a first reception panel and a second CRI orSSBRI is associated with a second reception panel.
 8. One or morenon-transitory computer-readable media storing instructions that, whenexecuted by one or more processors, are to cause a device to: determineconfiguration information associated with physical downlink controlchannel (PDCCH) monitoring from multiple transmission reception points(TRPs) by a user equipment (UE), wherein the configuration informationincludes an indication of multiple control resource sets (CORESETs)associated with a common transmission configuration indicator (TCI)group; and encode a message that includes the configuration informationfor transmission to the UE.
 9. The one or more non-transitorycomputer-readable media of claim 8, wherein the TCI group comprises TCIstates associated with a common reception panel.
 10. The one or morenon-transitory computer-readable media of claim 8, wherein the TCI groupincludes TCI states in different cells that are associated with a commonreception panel and have a common TCI state identifier.
 11. The one ormore non-transitory computer-readable media of claim 8, wherein the TCIgroup includes TCI states associated with CORESETs that are in turnassociated with a common CORESET pool index value and are associatedwith a common reception panel.
 12. The one or more non-transitorycomputer-readable media of claim 8, wherein the TCI group includes TCIstates that are associated with a common value of a panel index and areassociated with a common reception panel.
 13. The one or morenon-transitory computer-readable media of claim 8, wherein the TCI groupincludes two TCI states comprising a channel state information-referencesignal indicator (CRI) or a synchronization signal block resourceindicator (SSBRI) that are reported in a single reporting instance andare not associated with a common reception panel.
 14. The one or morenon-transitory computer-readable media of claim 13, wherein a first CRIor SSBRI is associated with a first reception panel and a second CRI orSSBRI is associated with a second reception panel.
 15. One or morenon-transitory computer-readable media storing instructions that, whenexecuted by one or more processors, are to cause a device to: determineconfiguration information that includes an indication of a first poolindex value of a control resource set (CORESET) and a second pool indexvalue of the CORESET, wherein the first pool index value is differentfrom the second pool index value; and encode a message for transmissionto a UE that includes the configuration information.
 16. The one or morenon-transitory computer-readable media of claim 15, wherein theconfiguration information is further to configure the UE for operationwith carrier aggregation in common frequency band.